home *** CD-ROM | disk | FTP | other *** search
- Path: noc.tor.hookup.net!not-for-mail
- From: gschmidt@noc.tor.hookup.net (Greg Schmidt)
- Newsgroups: comp.lang.c++
- Subject: Re: Watcom 10.0 #pragma and C++ class declarations
- Date: 11 Feb 1996 00:15:48 -0500
- Organization: HookUp Communication Corporation, Oakville, Ontario, CANADA
- Message-ID: <4fju24$tqm@noc.tor.hookup.net>
- References: <4fjcgd$omj@kdcol.kdcol.com>
- NNTP-Posting-Host: noc.tor.hookup.net
- NNTP-Posting-User: gschmidt
-
- In article <4fjcgd$omj@kdcol.kdcol.com>, Chad Barb <jestre@kdcol.com> wrote:
- >
- >I am trying to create a screen class in Watcom 10.0.
- >To do this, I need to use assembly, but I am unclear on the proper
- >syntax for in-class pragmas.
-
- First of all, why not use the int86/int386 functions? That's what they're
- there for (albeit a bit slower than direct assembly).
-
- Second, it makes a big difference whether you have a 16- or 32-bit target.
- "Inline assembly" (quoted, because Watcom doesn't do it like normal) is
- fairly easy (I think) with 16-bit targets, but much more difficult when
- you're working in a 32-bit world. These issues are discussed in some
- detail in the manuals (on-line and printed), but I can't remember exactly
- where right now.
-
- I would think that the pragmas for inside a class are the same as normal,
- but I have no experience to back that up.
- ------------------------------------------------------------------------------
- Greg Schmidt, Software Engineer, Mytec Technologies Inc., Toronto, Canada
- gschmidt@hookup.net gregs@trawna.UUCP http://www.hookup.net/~gschmidt/
-